Triple
T28743493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megalaimidae |
E731303
|
entity |
| Predicate | callFunction |
P30862
|
FINISHED |
| Object | territorial advertisement |
—
|
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: territorial advertisement | Statement: [Megalaimidae, callFunction, territorial advertisement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callFunction Context triple: [Megalaimidae, callFunction, territorial advertisement]
-
A.
apiFunction
Indicates that one entity is a callable operation or method provided by an API that another entity can invoke to perform a specific task or retrieve data.
-
B.
actualFunction
Indicates that something serves as the real, operative function or role performed in practice, as opposed to a nominal or theoretical one.
-
C.
publicFunction
Indicates that a function or method is accessible from outside its defining scope, module, or class (i.e., it has public visibility).
-
D.
functionInSystem
chosen
Indicates that an entity serves a specific role or performs a particular function within a given system.
-
E.
toolFunction
Indicates that one entity serves as a tool used to perform a particular function or achieve a specific purpose for 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f657b587288190804872c8ebbf94a4 |
completed | May 2, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_69f651ada6048190a7b4a6981565dc3a |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 6:03 a.m.