Triple
T7538762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Taylor |
E178216
|
entity |
| Predicate | hasNotableConsumerBase |
P77700
|
FINISHED |
| Object | fans of Elizabeth Taylor |
—
|
LITERAL 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: fans of Elizabeth Taylor | Statement: [House of Taylor, hasNotableConsumerBase, fans of Elizabeth Taylor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableConsumerBase Context triple: [House of Taylor, hasNotableConsumerBase, fans of Elizabeth Taylor]
-
A.
hasNotableReaderBase
Indicates that an entity is associated with a large, prominent, or otherwise noteworthy group of readers or audience.
-
B.
hasNotableHost
Indicates that an entity is associated with a host who is particularly prominent, famous, or otherwise noteworthy.
-
C.
hasNotableNative
Indicates that an entity is known for having a notable person, species, or element that originates from or is native to it.
-
D.
hasSupportBaseIn
Indicates that one entity maintains an operational or organizational base of support located in another entity.
-
E.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
- F. None of above. chosen
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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f87280f0819097d4ffc2e1b62cf8 |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f5cea2748190afd607ef93e8d66c |
completed | March 27, 2026, 9:25 p.m. |
Created at: March 27, 2026, 3:48 p.m.