Triple
T33862073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Sidney |
E867949
|
entity |
| Predicate | hasNotableMaleMember |
P304
|
FINISHED |
| Object | Sir Philip Sidney |
E104529
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Sir Philip Sidney | Statement: [House of Sidney, hasNotableMaleMember, Sir Philip Sidney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMaleMember Context triple: [House of Sidney, hasNotableMaleMember, Sir Philip Sidney]
-
A.
hasNotableMember
chosen
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
-
B.
hasNotableMaleBearer
Indicates that an entity has at least one well-known or prominent male individual associated with bearing its name or title.
-
C.
hasNotableSon
Indicates that an entity has a son who is recognized as notable or significant in some context.
-
D.
hasNotableCrewMember
Indicates that an entity is associated with a crew member who is considered notable or distinguished in some way.
-
E.
notableMale
Indicates that the subject is a male individual who is notable or well-known for some reason.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a021706e21c81909b83e2b4d9c4130c |
completed | May 11, 2026, 5:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3689c39d7481908a5d5fd908326294 |
completed | June 20, 2026, 12:38 p.m. |
| PD | Predicate disambiguation | batch_6a0216861214819097d2177755bc19d7 |
completed | May 11, 2026, 5:48 p.m. |
Created at: May 1, 2026, 1:47 a.m.