Triple
T38276668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prospekt Engelsa |
E1021977
|
entity |
| Predicate | hasNamedForField |
P17009
|
FINISHED |
| Object | political theory |
—
|
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: political theory | Statement: [Prospekt Engelsa, hasNamedForField, political theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamedForField Context triple: [Prospekt Engelsa, hasNamedForField, political theory]
-
A.
namedForField
chosen
Indicates that one entity is named after, or in honor of, a particular field, discipline, or area of study.
-
B.
hasNamedForRole
Indicates that an entity has been given a specific name or label that corresponds to a particular role it plays.
-
C.
fieldNamedFor
Indicates that a particular field (such as a sports field or open area) bears the name of a specified person, group, or entity in their honor.
-
D.
hasFieldName
Indicates that one entity is associated with, or identified by, a specific field name in a data structure or schema.
-
E.
namedForPersonField
Indicates that a field or area is named in honor of a specific person.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffdd05d1908190957deb11392f4595 |
completed | May 10, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69ffdc0d33c881908b3483bee8a96540 |
completed | May 10, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:30 p.m.