Triple
T21602211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The House on Q Street |
E533074
|
entity |
| Predicate | setInDomain |
P1248
|
FINISHED |
| Object | intelligence and espionage world |
—
|
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: intelligence and espionage world | Statement: [The House on Q Street, setInDomain, intelligence and espionage world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInDomain Context triple: [The House on Q Street, setInDomain, intelligence and espionage world]
-
A.
setInUniverse
Indicates that something is located within, belongs to, or takes place in a particular fictional or conceptual universe.
-
B.
usedInDomain
chosen
Indicates that something (such as a concept, method, or resource) is applied or utilized within a particular domain or field.
-
C.
replacedInDomain
Indicates that one entity has been superseded or substituted by another within a specific domain or contextual scope.
-
D.
setInPart
Indicates that something is located or placed within a specific part or section of a larger whole.
-
E.
setInOrganization
Indicates that an entity is located, based, or operating within a particular organization.
- 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e247588190a57f27ba04f4f21a |
completed | April 27, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:33 p.m.