Triple
T36609070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cité de la Muette housing complex |
E903418
|
entity |
| Predicate | functionBeforeWar |
P185611
|
FINISHED |
| Object | social housing estate |
—
|
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: social housing estate | Statement: [Cité de la Muette housing complex, functionBeforeWar, social housing estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionBeforeWar Context triple: [Cité de la Muette housing complex, functionBeforeWar, social housing estate]
-
A.
preBattleAction
Indicates an action or set of actions performed by an entity immediately before a battle or combat event.
-
B.
functionInWarfare
Indicates the role, purpose, or operational function that something serves within a military or warfare context.
-
C.
preparedBefore
Indicates that one entity was prepared or made ready at an earlier time than another entity.
-
D.
actsBefore
Indicates that one entity performs an action or occurs in time prior to another entity or action.
-
E.
functionDuringBattle
Indicates a functional role, effect, or behavior that specifically occurs or is active during a battle.
- F. None of above. chosen
Provenance (4 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c342de188190b4a26cd6f0c5d6b1 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1bbf5848190a698fdbec307886a |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c237bd1881908a00ea5ea17e7660 |
completed | May 3, 2026, 9:46 p.m. |
Created at: May 3, 2026, 4:11 p.m.