Triple
T32050330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thos. Greene |
E818473
|
entity |
| Predicate | refersToGenericPersonNamed |
P24766
|
FINISHED |
| Object | Thomas Greene |
—
|
NE NERFINISHED |
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: Thomas Greene | Statement: [Thos. Greene, refersToGenericPersonNamed, Thomas Greene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToGenericPersonNamed Context triple: [Thos. Greene, refersToGenericPersonNamed, Thomas Greene]
-
A.
refersToPerson
chosen
Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
-
B.
refersToPersonFrom
Indicates that one entity makes reference to, mentions, or is about a person originating from or associated with a particular place or group.
-
C.
refersToGenderOfPerson
Indicates that something specifies, denotes, or is associated with the gender of a particular person.
-
D.
refersToPersonKnownFor
Indicates that one entity makes reference to a person who is notable or recognized for some specific role, achievement, or characteristic.
-
E.
namedForPersonFullName
Indicates that an entity is named after a specific person, identified by that person’s full name.
- F. None of above.
Provenance (3 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 1, 2026, 12:20 a.m.