Triple
T33435171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web Linking |
E856222
|
entity |
| Predicate | registeredRelationsManagedBy |
P12071
|
FINISHED |
| Object | IANA |
—
|
NE NERFINISHED |
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: IANA | Statement: [Web Linking, registeredRelationsManagedBy, IANA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registeredRelationsManagedBy Context triple: [Web Linking, registeredRelationsManagedBy, IANA]
-
A.
managesRelationsWith
Indicates that one entity is responsible for handling, coordinating, or overseeing the interactions and ongoing relationship with another entity.
-
B.
recordsManagedBy
Indicates that certain records are overseen, maintained, or administered by a specified managing entity.
-
C.
registryManaged
Indicates that an entity is controlled, maintained, or overseen by a central registry or registration authority.
-
D.
relationshipManaged
chosen
Indicates that one entity oversees, directs, or maintains responsibility for the ongoing management of a relationship involving another entity.
-
E.
isManagedThrough
Indicates that one entity is administered, controlled, or operated by means of another entity, typically specifying the mechanism, channel, or system used for its management.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4857f3c819086399a37e954c6e9 |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.