Triple
T23920432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Institution of Structural Engineers |
E602198
|
entity |
| Predicate | awardsProfessionalTitle |
P2680
|
FINISHED |
| Object | Chartered Structural Engineer |
—
|
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: Chartered Structural Engineer | Statement: [Institution of Structural Engineers, awardsProfessionalTitle, Chartered Structural Engineer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardsProfessionalTitle Context triple: [Institution of Structural Engineers, awardsProfessionalTitle, Chartered Structural Engineer]
-
A.
isProfessionalAward
Indicates that the award in question is a formal recognition given within a professional or occupational context.
-
B.
awardsTitle
chosen
Indicates that an entity confers or grants a specific title or honorific designation to another entity.
-
C.
hasProfessionalTitleAuthority
Indicates that an entity has the formal authority to grant, assign, or recognize professional titles for other entities.
-
D.
creditedTitle
Indicates that a particular title or role is formally attributed to an entity as a credit.
-
E.
academicTitleOf
Indicates that one entity is the academic title or rank held by another entity.
- 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf1772e08190a434c91f4e7437b4 |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:41 p.m.