Triple
T9441464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | syndicat mixte |
E227654
|
entity |
| Predicate | canEmployStaff |
P58475
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [syndicat mixte, canEmployStaff, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canEmployStaff Context triple: [syndicat mixte, canEmployStaff, true]
-
A.
canHire
chosen
Indicates that one entity has the authority or ability to employ or recruit another entity.
-
B.
hasEmployees
Indicates that one entity employs one or more other entities as its workers or staff.
-
C.
mayWorkIn
Indicates that an entity is allowed or has the possibility to work in a particular place, organization, or context.
-
D.
employedPeople
Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
-
E.
usesStaffCode
Indicates that one entity performs an action or operates by referencing or applying a specific staff code associated with 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_69ca843884488190ad6cbe0153088234 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7ee4f4a08190ada5ee14fec2b822 |
completed | April 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:50 p.m.