Triple
T1511740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Fifth Republic |
E32027
|
entity |
| Predicate | allowsCohabitation |
P273
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [French Fifth Republic, allowsCohabitation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsCohabitation Context triple: [French Fifth Republic, allowsCohabitation, yes]
-
A.
canResideIn
Indicates that an entity is capable of living, staying, or being located within a specified place or environment.
-
B.
hasNonHumanResident
Indicates that a place or location is inhabited or occupied by one or more non-human entities.
-
C.
alsoTenant
Indicates that two or more entities share the status of being tenants, typically occupying the same property or rental arrangement.
-
D.
alsoTenantTo
Indicates that one entity is also a tenant of the same property or landlord as another entity, in addition to any other existing relationships.
-
E.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
- 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_69a885e8caf88190a5fbb6159ce87786 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9396e16408190b5e7b0ac43376d81 |
completed | March 5, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69a907aa67cc81909f00135365447399 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.