Triple
T21565368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Underground Man |
E532148
|
entity |
| Predicate | relationshipToSociety |
P9470
|
FINISHED |
| Object | withdrawn |
—
|
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: withdrawn | Statement: [Underground Man, relationshipToSociety, withdrawn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToSociety Context triple: [Underground Man, relationshipToSociety, withdrawn]
-
A.
relationshipToHeed
Indicates a relationship in which one entity is expected to pay attention to, respect, or follow the guidance, warnings, or wishes of another entity.
-
B.
livesInSocietyType
Indicates that an entity resides within or is a member of a particular type or category of society.
-
C.
hasViewOnSociety
chosen
Indicates that an entity holds a particular perspective, opinion, or stance regarding society or social structures.
-
D.
society
Indicates a relationship in which individuals or groups are organized into a structured community bound by shared institutions, norms, or social systems.
-
E.
societalOrganization
Indicates how a society is structured and organized in terms of its institutions, roles, and social relationships.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2e777c881908de84493fa939ff3 |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.