Triple
T4020573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chartered Engineer |
E91269
|
entity |
| Predicate | isRegisteredWith |
P2830
|
FINISHED |
| Object | professional engineering institution |
—
|
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: professional engineering institution | Statement: [Chartered Engineer, isRegisteredWith, professional engineering institution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegisteredWith Context triple: [Chartered Engineer, isRegisteredWith, professional engineering institution]
-
A.
hasRegister
Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
-
B.
supportsRegistration
Indicates that an entity provides the capability or functionality to handle or accept registration actions or processes.
-
C.
hasStandardRegister
Indicates that something is expressed or occurs in a standard, neutral, or non-marked linguistic register.
-
D.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
E.
relatedRegister
Indicates a relationship where one entity is associated with, linked to, or corresponds to a particular register or record in a system.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.