Triple
T10797755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoav Nir |
E254754
|
entity |
| Predicate | roleInRFC7539 |
P28582
|
FINISHED |
| Object | co-author |
—
|
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: co-author | Statement: [Yoav Nir, roleInRFC7539, co-author]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInRFC7539 Context triple: [Yoav Nir, roleInRFC7539, co-author]
-
A.
roleIn3GPP
Indicates that an entity holds a specific role or function within the context of 3GPP (Third Generation Partnership Project) standards or activities.
-
B.
canonicalRole
Indicates that an entity holds a standard, primary, or officially recognized role within a particular context or system.
-
C.
acknowledgesRoleOf
Indicates that one entity explicitly recognizes and accepts the position, function, or authority that another entity holds.
-
D.
roleInStandards
chosen
Indicates that an entity holds a specific role or function in the creation, maintenance, or governance of standards.
-
E.
roleInProtocolStack
Indicates the specific function or position an entity occupies within a layered communication or protocol stack.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d73333dc4081909faa40c10bce2735 |
completed | April 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.